We have two exchange server in two domains sharing the same e-mail name space. We have been successfully using the "Forward all mail with unresolved recipients to host" feature for over a year when it seems to have suddenly stopped working. Now when we send messages to recipients on the other exchange server, we receive NDRs. The messages do not appear to be getting out of the exchange server (2003). An NDR is generated shortly after the message is Categorized and Queued. They never seem to get to the "Routed and Queued for remote delivery". I can ping the remote host and I have tested the remote SMTP server via telnet and it accepts and delivers messages. Our server accepts and delivers messages but not via the "Forward all unresolved" method. Our server can also deliver messages to an alternate address space on the remote server. There are no errors in the event viewer. Messages are not stuck in queue. I have reset the server, reset the services, killed off services, etc to no avail. It appears to have stopped working June 11. It worked briefly this morming between 12 AM and mid morning. Also, SMTP log entries seem to have stopped after 7:32 on June 11th, 2010. We have made no intentional changes in our Exchange server configuration recently. I would appreciate any debugging assistance one can lend.

What does the NDR say? Verify that the recipient policy doesn't have the e-mail domain configured such that Exchange is responsible for all mail, i.e., ensure that Exchange is not authoritative for the domain. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "mdevine1205" wrote in message news:466d895b-261f-4cef-b415-b62fd0f1a04c... We have two exchange server in two domains sharing the same e-mail name space. We have been successfully using the "Forward all mail with unresolved recipients to host" feature for over a year when it seems to have suddenly stopped working. Now when we send messages to recipients on the other exchange server, we receive NDRs. The messages do not appear to be getting out of the exchange server (2003). An NDR is generated shortly after the message is Categorized and Queued. They never seem to get to the "Routed and Queued for remote delivery". I can ping the remote host and I have tested the remote SMTP server via telnet and it accepts and delivers messages. Our server accepts and delivers messages but not via the "Forward all unresolved" method. Our server can also deliver messages to an alternate address space on the remote server. There are no errors in the event viewer. Messages are not stuck in queue. I have reset the server, reset the services, killed off services, etc to no avail. It appears to have stopped working June 11. It worked briefly this morming between 12 AM and mid morning. Also, SMTP log entries seem to have stopped after 7:32 on June 11th, 2010. We have made no intentional changes in our Exchange server configuration recently. I would appreciate any debugging assistance one can lend. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, Did you check the Message Tracking log? You can also post it here. Thanks Allen